Important: The commands or keywords/variables that are available are dependent on platform type, product version, and installed license(s).priority must be an integer from 1 through 15.
pci pci_value
pci_value must be integer 0 or 1.
Important: If not explicitly enabled, then the default value of 1 will hold true.pvi pvi_value
pvi_value must be integer 0 or 1.
Important: If not explicitly enabled, then the default value of 0 will hold true.billing-action { edr edr_format_name [ wait-until-flow-ends ] | egcdr | exclude-from-udrs | radius | rf } +
billing-action { create-edrs { charging-edr charging_edr_format_name | reporting-edr reporting_edr_format_name } + [ wait-until-flow-ends ] | egcdr | exclude-from-udrs | radius | rf } +
Important: This option is available only in 12.1 and earlier releases. In 12.2 and later releases, it is deprecated and is replaced by the create-edrs charging-edr option.edr_format_name must be the name of an existing EDR format, and must be an alphanumeric string of 1 through 63 characters.
Important: If the EDR format name specified here is not configured in the EDR Format Configuration Mode, or has been deleted, the system accepts it without applying any EDR format for the billing action in this ACS service.wait-until-flow-ends: By default, the EDR is generated immediately after a ruledef hit results in this charging action. When this keyword is specified, no EDR is generated on a ruledef hit. When the flow ends, an attempt is made to generate an EDR with the format specified.
create-edrs { charging-edr charging_edr_format_name | reporting-edr reporting_edr_format_name } + [ wait-until-flow-ends ]
Important: This option is available only in 12.2 and later releases.|
•
|
charging-edr charging_edr_format_name: Specifies to generate charging EDR.
|
charging_edr_format_name must be the name of a charging EDR format, and must be an alphanumeric string of 1 through 63 characters.
|
•
|
reporting-edr reporting_edr_format_name: Specifies to generate reporting EDR.
|
reporting_edr_format_name must be the name of a reporting EDR format, and must be an alphanumeric string of 1 through 63 characters.
|
•
|
wait-until-flow-ends: By default, the EDR is generated immediately after a ruledef hit results in this charging action. When this keyword is specified, no EDR is generated on a ruledef hit. When the flow ends, an attempt is made to generate an EDR with the format specified.
|
To generate an eG-CDR the accounting-mode command in the APN Configuration Mode must be configured with the “none” option.
The format of enhanced G-CDRs is controlled by the inspector CLI command in the Context Configuration Mode.
By default, statistics are accumulated on a per content ID basis for possible inclusion in UDRs. The exclude-from-udrs keyword causes the system to not include the packet’s statistics in UDRs.
Rf accounting is applicable only for dynamic and predefined rules that are marked for it. Dynamic rules have a field offline-enabled to indicate this. To mark a predefined rule as offline-enabled, use this keyword and the billing-records CLI in the ACS Rulebase Configuration Mode.
in 12.1 and earlier releases, the following command enables the EDR billing type with EDR format charge1_format:
rating-group coupon_id
coupon_id must be an integer from 0 through 65535.
Important: This rating-group overrides the content ID, if present in the same charging-action for the prepaid customer in Diameter Credit Control Application (DCCA). But only the content IDs will be used in eG-CDRs irrespective of the presence of rating-group in that charging action.charge-units units
Default: 0; disables the counter, same as no charge-units
units is the value set for charging unit, and must be an integer from 1 through 65535.
Important: For more information on content ID, refer to the if-protocol command in the ACS Ruledef Configuration Mode Commands chapter.Default: charge-volume ip bytes
|
•
|
dns: Charge volume for DNS
|
|
•
|
ftp-control: Charge volume for FTP-Control
|
|
•
|
ftp-data: Charge volume for FTP-Data
|
|
•
|
http: Charge volume for HTTP
|
|
•
|
icmp: Charge volume for ICMP
|
|
•
|
imap: Charge volume for Internet Message Access Protocol (IMAP)
|
|
•
|
ip: Charge volume for IP
|
|
•
|
mms: Charge volume for MMS
|
|
•
|
pop3: Charge volume for POP3
|
|
•
|
pptp: Charge volume for PPTP
|
|
•
|
rtcp: Charge volume for RTCP
|
|
•
|
rtp: Charge volume for RTP
|
|
•
|
rtsp: Charge volume for RTSP
|
|
•
|
sdp: Charge volume for SDP
|
|
•
|
secure-http: Charge volume for secure-https
|
|
•
|
sip: Charge volume for SIP
|
|
•
|
smtp: Charge volume for SMTP
|
|
•
|
tcp: Charge volume for TCP
|
|
•
|
tftp: Charge volume for TFTP
|
|
•
|
udp: Charge volume for UDP
|
|
•
|
wsp: Charge volume for WSP
|
|
•
|
wtp: Charge volume for WTP
|
constant fixed_value
fixed_value is the value set for charging, and must be an integer from 0 through 65535.
If constant 3 is configured for every invocation of this Charging Action, the system adds 3 to the downlink/uplink volume counter, depending on the direction of packet.
For information on supported protocols see the ACS Ruledef Configuration Mode Commands chapter.
If charge-volume rtp packets is configured, system computes volume amounts for different options for RTP as follows:
Important: Whenever service counts volume, it counts all packets that the relevant analyzers accepted.
Important: If a TCP packet is routed to the HTTP analyzer but there is no HTTP payload, then the TCP statistics will be updated but the HTTP statistics will not be updated (except for the “packets ignored by the HTTP analyzer” statistic).This command works as second-level filter to process the HTTP/WAP GET request with Internet Content Adaptation Protocol (ICAP) after ruledef matching. The first-level filtering is in the rulebase configuration. This CLI command is only effective when the content-filtering mode server-group command is configured in the rulebase.
content-id content_id
In 12.1 and earlier releases content_id must be an integer from 1 through 65535.
In 12.2 and later releases, content_id must be an integer from 1 through 2147483647.
If the specified ruledef uses the if-protocol command to select a value for content ID, then the content_id specified through this command is not used for billing record generation.
Important: For more information on content-id, refer to the if-protocol command in the ACS Ruledef Configuration Mode Commands chapter.flow action { conditional user-agent end-token end_token_name | discard [ downlink | uplink ] | random-drop interval interval_start to interval_end pkts-to-drop packet_min to packet_max | redirect-url redirect_url [ clear-quota-retry-timer ] | readdress [ server ipv4_address ] [ port port_number ] | terminate-flow | terminate-session }
flow action { conditional user-agent end-token end_token_name | discard [ downlink | uplink ] | random-drop interval interval_start to interval_end pkts-to-drop packet_min to packet_max | readdress [ server ipv4_address ] [ port port_number ] | redirect-url redirect_url [ [ encryption { blowfish128 | blowfish64 } [ encrypted ] key key ] clear-quota-retry-timer ] | terminate-flow | terminate-session }
conditional user-agent end-token end_token_name
Specifies to conditionally redirect the HTTP packets matched to a configured user-agent to a specified URL. The user agent is configured using the redirect user-agent command in the ACS Configuration Mode.
end_token_name must be an alphanumeric string of 1 through 32 characters, and is configured with this command to end the redirection condition.
|
•
|
downlink: Downlink packets
|
|
•
|
uplink: Uplink packets
|
Specifies to drop a group of consecutive packets (pkts-to-drop) to be dropped in the specified time interval (random-drop interval). This will cause degradation in user experience. P2P VoIP would need more than one packet to be dropped, since that type of protocol is geared to handle occasional single packet drops.
|
•
|
random-drop interval interval_start to interval_end: Specifies the random drop interval, in seconds, at which the voice packets will be dropped.
|
interval_start and interval_end must be integers from 1 through 999.
|
•
|
pkts-to-drop packet_min to packet_max: Specifies the number of voice packets to be dropped at a time in a flow when the packets have to be dropped.
|
packet_min and packet_max must be integers from 1 through 100.
|
•
|
ipv4_address specifies the re-address server’s IPv4 address.
|
|
•
|
port_number must be the re-address server’s port number, and must be an integer from 1 through 65535.
|
redirect-url redirect_url [ [ encryption { blowfish128 | blowfish64 } [ encrypted ] key key ] clear-quota-retry-timer ]
Specifies to return a redirect response to the subscriber, and terminate the TCP connections (to the subscriber and server). The subscriber's Web browser should automatically send the original HTTP packet to the specified URL. Redirection is only possible for certain types of HTTP packets (for example, GET requests), which typically are only sent in the uplink direction. If the flow is not HTTP, the redirect-url option is ignored, that is the packet is forwarded normally, except for SIP. For SIP, a Contact header with the redirect information is inserted.
|
•
|
redirect_url specifies the redirect URL. redirect_url must be an alphanumeric string of 1 through 511 characters. It may include one or more dynamic fields (up to 16 may be specified). For example, http://search.com/subtarg=#HTTP.URL#.
|
|
•
|
encryption: Specifies to enable encryption for dynamic fields of redirect URL.
|
|
•
|
blowfish128: Specifies to use Blowfish encryption with 28 bit key for encrypting the dynamic fields.
|
|
•
|
blowfish64: Specifies to use Blowfish encryption with 64 bit key for encrypting the dynamic fields.
|
|
•
|
encrypted: Specifies to encrypt the key.
|
|
•
|
key key: Specifies key to use for encryption of dynamic fields.
|
key must be an alphanumeric string of 1 through 523 characters.
|
•
|
clear-quota-retry-timer: Specifies to reset Credit Control Application (CCA) Quota Retry Timer upon redirection.
|
%3furl= can be used as a delimiter between URL. As in http://search.com/subtarg/%3furl=#HTTP.URL# format.
When a readdress server is configured for a charging action, the show configuration command will display the readdress related configuration only if server address is configured. The show configuration verbose command will display the readdress sever if configured, else will display “no flow action”.
charging-action ca_sip_redir
content-id 10
flow action redirect-url sip:test@sip.org
ruledef sip_req
rulebase plan1
This would mean any SIP request that hits the sip_req ruledef, would get redirected to the url given in ca_sip_redir. This involves creating a redirection packet with the following response line and “Contact” header in the response.
The following command resets quota retry timer upon redirection of flow to HTTP URL http://search.com/?url=#http://msn.com#:
idle-timeout idle_timeout
idle_timeout must be an integer from 0 through 86400.
flow-mapping flow_timeout
flow_timeout must be an integer from 0 through 86400.
flow limit-for-bandwidth { { direction { downlink | uplink } peak-data-rate bps peak-burst-size bytes violate-action { discard | lower-ip-precedence } [ committed-data-rate bps committed-burst-size bytes [ exceed-action { discard | lower-ip-precedence } ] ] } | { id id } }
|
•
|
downlink: Flow of data towards subscriber.
|
|
•
|
uplink: Flow of data from subscriber.
|
peak-data-rate bps
bps must be an integer from 1 through 4294967295.
peak burst-size bytes
bytes must be an integer from 1 through 4294967295.
Important: It is recommended that this parameter be configured to at least the greater of the following two values: 1) three times greater than packet MTU for the subscriber connection, OR 2) three seconds worth of token accumulation within the “bucket” for the configured peak-data-rate.|
•
|
discard: Discard the packet
|
|
•
|
lower-ip-precedence: Transmit the packet after lowering the IP precedence
|
Default: discard
bps must be an integer from 1 through 4294967295.
committed-burst-size bytes
bytes must be an integer from 1 through 4294967295.
|
•
|
discard: Discard the packet
|
|
•
|
lower-ip-precedence: Transmit the packet after lowering the ip-precedence
|
Default: lower-ip-precedence
id id
Important: This keyword is only available in 8.1 and later releases.id must be an integer from 1 through 65535.
Important: If the exceed/violate action is set to “lower-ip-precedence”, the TOS value for the outer packet becomes “best effort” for packets that exceed/violate the traffic limits regardless of what the ip user-datagram-tos copy command is configured to. In addition, the lower-ip-precedence option may also override the ip qos-dscp command configuration. Therefore, it is recommended that command not be used when specifying this option.More information on the QoS feature is available in the QoS Management appendix of the System Administration Guide.
The following command sets an uplink peak data rate of 128000 bps and lowers the IP precedence when the committed-data-rate and the peak-data-rate are exceeded:
The following command sets a downlink peak data rate of 256000 bps and discards the packets when the committed-data-rate and the peak-data-rate are exceeded:
flow limit-for-flow-type limit over-limit-action { discard | redirect-url | terminate-flow | terminate-session }
limit must be an integer from 1 through 4000000000.
Specifies the action to take on exceeding limit for a flow type:
|
•
|
discard: Discards the packets
|
|
•
|
redirect-url: Redirects the flow
|
|
•
|
terminate-flow: Terminates the flow to which this packet belongs
|
|
•
|
terminate-session: Terminates the session to which this packet belongs
|
If the flow is not HTTP, the redirect-url option is ignored, that is the packet is forwarded normally. Refer to the flow action CLI command.
If the limit specified by the flow limit-across-applications command in the Rulebase Configuration Mode is also exceeded, action is taken for that over-limit condition rather than the action configured here.
ip tos { af11 | af12 | af13 | af21 | af22 | af23 | af31 | af32 | af33 | af41 | af42 | af43 | be | ef | lower-bits tos_value } [ uplink | downlink ]
af xx
Specifies the use of an assured forwarding xx per hop behavior (PHB).
lower-bits tos_value
Important: In StarOS 8.1 and later releases, this keyword is “lower-bits tos_value”. In StarOS 8.0, it is tos_value.tos_value must be an integer from 0 through 63.
ip vlan vlan_id
Default: Disable this IP VLAN configuration. Same as no ip vlan command.
vlan_id must be an integer from 1 through 4094.
nexthop-forwarding-address ipv4_address
ipv4_address must be the nexthop forwarding address, and must be an IPv4 address.
The following command sets the nexthop forwarding address for the current charging action to 10.1.1.1:
qos-class-identifier qos_class_identifier
qos_class_identifier must be an integer from 1 through 9 or from 128 through 254 (Operator specific).
Important: This command is license dependent. For more information please contact your Cisco account representative.interactive priority
priority specifies the traffic handling priority, and must be an integer from 1 through 3.
Default: Disabled; same as no retransmissions-counted
service-identifier service_id
In 12.1 and earlier releases service_id must be an integer from 1 through 65535.
In 12.2 and later releases, service_id must be an integer from 1 through 2147483647.
[ no ] tft packet-filter packet_filter_name
packet_filter_name must be the name of a packet filter, and must be an alphanumeric string of 1 through 63 characters.
The following command configures the packet filter filter23 to be sent to the MS:
tos { af11 | af12 | af13 | af21 | af22 | af23 | af31 | af32 | af33 | af41 | af42 | af43 | be | ef | lower-bits tos_value } [ downlink | uplink ]
af xx
Specifies the use of an assured forwarding xx Per Hop Behavior (PHB).
lower-bits tos_value
Important: In 8.1 and later releases, this keyword is “lower-bits tos_value”. In 8.0 release, it is tos_value.tos_value must be an integer from 0 through 63.
The following command sets the ToS to be for downlink packets:
tpo profile tpo_profile_name
tpo_profile_name must be the name of a TPO profile, and must be an alphanumeric string of 1 through 63 characters.
The following command configures a TPO profile named tpoprofile10 for the current charging action:
video bitrate bit_rate
bit_rate must be an integer from 0 to 256000000.
The following command sets the bit rate for the video flow at 300000 (300kbps):
xheader-format xheader_format_name
xheader_format_name must be an alphanumeric string of 1 through 63 characters.
[ default | no ] video pacing by-policing [ initial-burst-duration value | normal-burst-duration value ][ -noconfirm ]
Enables the video pacing feature. When enabled, video pacing is applied per TCP video flow. The command syntax by-policing enables pacing enforcement by the policing method, which is the available method for this software release.
initial-burst-duration value
value must be an integer between 1 and 30.
normal-burst-duration value
value must be an integer between 1 and 30.
video transrating target-rate-reduction percentage_of_input_rate
video transrating target-rate-reduction percentage_of_input_rate
Important: This command is license dependent. For more information please contact your Cisco account representative.xheader-insert xheader-format xheader_format_name [ encryption rc4md5 [ encrypted ] key key ] [ first-request-only ] [ -noconfirm ]
xheader-format xheader_format_name
xheader_format_name must be the name of an x-header format, and must be an alphanumeric string of 1 through 63 characters.
key specifies the key as an alphanumeric string of 8 through 15 characters.
encryption specifies use of encryption.
The key can be configured either as plain text or encrypted. However, in the output of the show configuration command it will always be displayed as encrypted. And, in the output of the show configuration showsecrets command it will be displayed as plain text.
Also, see the xheader-format command in the ACS Configuration Mode Commands and ACS X-header Format Configuration Mode Commands chapters.
